Repository navigation
Dr.Egeria updates no longer reset properties the document doesn't set (ISSUE-162) - #482
Merged
dwolfson merged 3 commits intoOct 23, 2026
Merged
Conversation
…s to False Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
…t set (ISSUE-162) Update Glossary Term sent isAbstractConcept/isActivityDescription/ isContext/isDataValue = False whenever the document omitted them, and Update Data Value Specification / Data Class sent allowsDuplicateValues / isNullable = True plus empty lists/maps/0 for matchPropertyNames, matchThreshold, specificationDetails, sampleValues, dataPatterns and additionalProperties. Merge updates dropped only None, so these overwrote existing values. They now default to None (omitted on a merge update, which Egeria defaults to); the old defaults are applied only on Create, so creation is unchanged. Micro-tests: tests/micro-tests/test_issue_162_update_does_not_reset_properties.py (update cases fail on the old code). Full micro-test suite passes in a clean python:3.13-slim container. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
…properties) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
dwolfson
added a commit
to dwolfson/egeria-python
that referenced
this pull request
Oct 23, 2026
…lass-names Resolved the only conflict, PYEGERIA_ISSUES.md: both PRs inserted entries at the top of "Open pyegeria items". Kept both, newest first: ISSUE-165, 164, 163, then 162. Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
This was referenced Oct 23, 2026
dwolfson
added a commit
that referenced
this pull request
Oct 28, 2026
* docs(issues): re-sort the issue trackers, open items first PYEGERIA_ISSUES.md: - Released fixes still marked "not yet released" now name the PR and release: ISSUE-111/113/129/134/136 (#446) and ISSUE-135 (#445) in 6.2.2, ISSUE-153 (#460) 6.2.5, ISSUE-160 (#474/#475 6.2.8, #478 6.2.9), ISSUE-161 (#477) 6.2.9, ISSUE-162 (#482) and ISSUE-163/164 (#483) 6.2.10. ISSUE-166 notes the pyegeria side (#498, 6.2.13). - Moved the fixed entries (ISSUE-153, 160-166) from the open sections to the top of Fixed / Resolved. - Awaiting re-test is now a real section after the open ones, holding ISSUE-125, 124, 117, 112, 90, 95 and 89. Its old header sat in the middle of the Fixed list, where everything under it except ISSUE-95 and ISSUE-89 was already fixed. - The At-a-glance counts and lists are rebuilt from the section contents (14 open pyegeria items, 7 awaiting re-test, 5 open Egeria Server issues), and the re-test section notes the quickstart now runs Egeria main abe31272. EGERIA_OPEN_ISSUES.md: drop the fixed ISSUE-166 entry, and move ISSUE-79 (Egeria needs information) and ISSUE-38 (pending oak2026 merge) out of Awaiting re-test, matching their 2026-10-18 status. No entry text was removed: 166 entries before and after. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015pdMuTg6FmqPWeapeXM54g Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com> * docs(issues): ISSUE-165 released in 6.2.11 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015pdMuTg6FmqPWeapeXM54g Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com> --------- Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes ISSUE-162 (PYEGERIA_ISSUES.md; the entry is added in this PR): Dr.Egeria updates reset properties the document didn't mention.
Problem
Merge updates (Egeria's default) drop only
Nonevalues, so any property with a non-Nonedefault was sent on every update and overwrote Egeria's existing value:isAbstractConcept,isActivityDescription,isContextandisDataValueasFalse. A term with any of these set lost it on an unrelated update. Found by Resource Explorer while preparing a 96-term update batch.allowsDuplicateValuesandisNullableasTrue,matchPropertyNames,sampleValuesanddataPatternsas[],matchThresholdas0, andspecificationDetailsandadditionalPropertiesas{}.Change
None, so a merge update leaves them out unless the document sets them. Egeria'smergeUpdatedefaults totrue, so the existing values are kept._with_create_defaultsinmd_processing/v2/data_designer.py, and the term flags inmd_processing/v2/glossary.py), so creation behaves as before.Testing
tests/micro-tests/test_issue_162_update_does_not_reset_properties.py: 7 cases. The 4 update cases fail on the old code; the 3 create cases check the create defaults are unchanged.python:3.13-slimcontainer with no Egeria.🤖 Generated with Claude Code